RNS.recipes Forum - /page/forum/thread.mu

Micron Document

✓ RNS 1.4.2 released https://pypi.org/project/rns/

🬤 rns.recipes

Forum / Help / lxmd and rnsd service

top

╔═══════════════════════════════════════════════════════════════════════════════════════════════════╗

║ lxmd and rnsd service ║

╚═══════════════════════════════════════════════════════════════════════════════════════════════════╝

Started by Anonymous · 4mo ago

↓ Jump to bottom · Export as .md

Page 1 of 2

[ 1 ] Next >

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

post-1

╭───────────────────────────────────────────────────────────────────────────────────────────────╮

│ Anonymous #1 │

╰───────────────────────────────────────────────────────────────────────────────────────────────╯

▸ 4mo ago

Hi,

can you share how your rnsd+lxmd setup looks like? I currently have both running as

systemd service files, but on bootup lxmd does not boot properly for some reason. I have

to stop it and then start it again so it works.

Here are my service files:

lxmd:

# /etc/systemd/system/lxmd.service

[Unit]

Description=LFXC daemon propagation node

Requires=rnsd.service

After=rnsd.service

[Service]

Type=simple

Restart=always

RestartSec=3

User=rns

ExecStart=/home/rns/.local/bin/lxmd --propagation-node --service

[Install]

WantedBy=multi-user.target

and rnsd:

# /etc/systemd/system/rnsd.service

[Unit]

Description=Reticulum Network Stack Daemon

After=multi-user.target

[Service]

# If you run Reticulum on WiFi devices,

# or other devices that need some extra

# time to initialise, you might want to

# add a short delay before Reticulum is

# started by systemd:

# ExecStartPre=/bin/sleep 10

Type=simple

Restart=always

RestartSec=3

User=rns

ExecStart=/home/rns/.local/bin/rnsd --service

[Install]

WantedBy=multi-user.target

↑ 0 ↓ 0 ❤ 0

↑ top · next post ↓

post-2

│ LinuxinaBit #2 │

▸ 4mo ago

To troubleshoot, it's worth running:

systemctl status lxmd.service

I recommend just starting NomadNet with systemd and letting it handle the rest.

To start nomadnet in daemon mode, use:

nomadnet --daemon

↑ 1 ↓ 0 ❤ 0

↑ top · next post ↓

post-3

│ Anonymous #3 │

▸ 4mo ago

I am a bit confused how the daemons work with each other, maybe because the documentation

is very bare on this side. You mean by starting nomadnet it would also start rnsd and a

propagation node?

↑ 0 ↓ 0 ❤ 1

↑ top · next post ↓

post-4

│ Anonymous #4 │

▸ 4mo ago

Aha, I see. lxmd seems to start up rnsd automatically. I removed the rnsd service file

and instead start now only lxmd. seems to work.

↑ 1 ↓ 0 ❤ 1

↑ top · next post ↓

post-5

│ Basil #5 │

│ 0acddbcdcf2702f3 │

▸ 4mo ago

hi!!, for rnsd, i use

[Unit]

Description=Reticulum Network Stack Daemon

After=network.target

[Service]

ExecStart=<folderwherernsislocatedin>/rnsd

Restart=always

User=<yourusername>

[Install]

WantedBy=multi-user.target

↑ 0 ↓ 0 ❤ 1

↑ top · next post ↓

post-6

│ aaaa #6 │

│ abcsdfgasdasdfda │

▸ 4mo ago

test

↑ 0 ↓ 0 ❤ 0

↑ top · next post ↓

post-7

│ K8 #7 │

▸ 3mo ago

None of these are reliable options. You need to watch the logs to know when RNS is fully

started and it's ok to start lxmd and NomadNet. To do that you need wrapper scripts that

fork off the rnsd process and don't end themselves until the logs indicate that RNS is

fully started. This allows you to use the systemd functionality for making sure the

different services start in sequence, without having to rely on timers which will get

flaky when RNS has to load a lot of path table entries on startup.

** /etc/systemd/system/rnsd.service **:

[Unit]

Description=Reticulum rnsd Service

After=network-online.target

Requires=network-online.target

StartLimitIntervalSec=60

StartLimitBurst=4

[Service]

Type=forking

ExecStart="/path/to/start_rnsd.sh"

ExecStop="/path/to/stop_rnsd.sh"

Restart=always

RestartSec=3

Nice=-10

Environment="PYTHONPATH='/home/rns/Reticulum':'/home/rns/LXMF':'/home/rns/NomadNet'"

WorkingDirectory=~

User=rns

Group=reticulum

[Install]

WantedBy=multi-user.target

** start_rnsd.sh **:

#!/bin/bash

set -e

LOG="/path/to/reticulum/logfile"

LOGLINES=0

if [ -f $LOG ]; then

LOGLINES=$(wc -l < $LOG)

echo "Starting rnsd service"

export PYTHONPATH='/home/rns/Reticulum':'/home/rns/LXMF':'/home/rns/NomadNet'

python3 -m "RNS.Utilities.rnsd" --service --config "/home/rns/config/reticulum" &

echo "Waiting for rnsd service to fully start"

while true; do

NEWLOGLINES=$(wc -l < $LOG)

if [ "$NEWLOGLINES" -lt "$LOGLINES" ] ; then

# The log must have rotated since the start of the script

TAILCMD="cat $LOG"

else

TAILCMD="tail -n +$LOGLINES $LOG"

if $($TAILCMD | grep -q -E "Started rnsd"); then

break

else

sleep 1

done

echo "Started rnsd service"

** stop_rnsd.sh **

#!/bin/bash

set -e

LOG="/path/to/reticulum/logfile"

LOGLINES=0

if [ -f $LOG ]; then

LOGLINES=$(wc -l < $LOG)

echo "Stopping rnsd service"

kill $MAINPID

echo "Waiting for rnsd service to fully shut down"

while true; do

NEWLOGLINES=$(wc -l < $LOG)

if [ "$NEWLOGLINES" -lt "$LOGLINES" ] ; then

# The log must have rotated since the start of the script

TAILCMD="cat $LOG"

else

TAILCMD="tail -n +$LOGLINES $LOG"

if $($TAILCMD | grep -q -E "Saved known destinations to storage"); then

break

else

sleep 1

done

echo "Stopped rnsd service"

Note that I run my node from source for easier development, so you'll have to change the

command to run rnsd to whatever you need for your environment, and you can also remove

the Environment=... line from the service file.

The lxmd service definition will look similar, but depending on the rnsd service:

After=rnsd.service

Requires=rnsd.service

And the start and stop scripts should grep for "Started lxmd" and "All interfaces

detached", respectively (and naturally should be changed to run the right command).

For NomadNet, grep for "ready for incoming connections" and "Persisting LXMF state data

to storage".

I have all of this abstracted in an Ansible playbook that I use to deploy my public node.

I will release it at some point, once I get things cleaned up and documented a bit.

↑ 0 ↓ 0 ❤ 2

↑ top · next post ↓

post-8

│ Anonymous #8 │

▸ 3mo ago

Thank you for sharing! This is more complicated then I hoped ^^ but makes sense that it

will work that way.

↑ 0 ↓ 0 ❤ 0

↑ top · next post ↓

post-9

│ joakim #9 │

▸ 3mo ago

I just check for port 4242 being open before starting lxmd . In

lxmd.service :

ExecStartPre=/usr/bin/bash -c '(while ! ss -lnt sport = :4242 | grep 4242 2>/dev/null; do echo "Waiting for port 4242 to open..."; sleep 3; done); sleep 3'

K8's solution is more thorough though, and I would think more reliable. The port being

open doesn't necessarily mean that rnsd is ready, so YMMV, but it has

worked well for me so far.

↑ 1 ↓ 0 ❤ 0

↑ top · next post ↓

post-10

│ joakim #10 │

▸ 3mo ago

Anonymous wrote:

> I am a bit confused how the daemons work with each other, maybe because the

documentation is very bare on this side. You mean by starting nomadnet it would also

start rnsd and a propagation node?

It's explained here: https://reticulum.miraheze.org/wiki/RNS#Shared_instance

Running (only) lxmd sounds like the right choice for you.

nomadnet seems to have memory leaks, so I'd not run that as a daemon unless I also

needed to serve pages/files. (Edit: Not sure whether this is still an issue.)

Running rnsd first makes sense in some situations. From the manual:

> If you are running Reticulum on a system with several different programs that use RNS

starting and terminating at different times, it will be advantageous to run a master RNS

instance as a daemon for other programs to use on demand.

↑ 0 ↓ 0 ❤ 0

↑ top

[ 1 ] Next >

Page 1 of 2

░ INFO ⚠ Identify to this node to post. How?

bottom

↑ Jump to top

< Help | < Forum